In my formal module there are 4 groups of functional requirements. Of course the DOORS built-in identifier enumerates all objects regardless the functionality.
So how can I build 4 identifiers, one for each functionality? I need these identifiers to have the same basic properties of the built-in identifier: unique numbers, preserved number for deleted requirements,....
Of course the easiest solution is to split the module in 4 separated modules Is there a way to achieve my goal with some layout DXL or trigger or anything? Thanks pvselex - Tue Mar 29 08:00:31 EDT 2016 |
Re: Multiple independent identifiers I suggest you base your solution on the DOORS Absolute number. Just like DOORS join it with a module prefix to get the Object Identifier you can join it with different prefixes for each of your "Functional groups".
You can use a DXL attribute with the following one line of code: obj.attrDXLName = obj."Functional Group" "_" obj."Absolute Number" ""
Of course you can elaborate for example by only assigning identities to objects that have been assigned to a functional Group. In this solution the identifiers are not really independent. But why should they be? A requirement id is just a persistent unique tag. Ordered numbers are just an easy way to accomplish that. And in this case if you switch functional group the number part of your identity will still be the same, which is a good thing.
|
Re: Multiple independent identifiers morast - Thu Mar 31 04:49:51 EDT 2016 I suggest you base your solution on the DOORS Absolute number. Just like DOORS join it with a module prefix to get the Object Identifier you can join it with different prefixes for each of your "Functional groups".
You can use a DXL attribute with the following one line of code: obj.attrDXLName = obj."Functional Group" "_" obj."Absolute Number" ""
Of course you can elaborate for example by only assigning identities to objects that have been assigned to a functional Group. In this solution the identifiers are not really independent. But why should they be? A requirement id is just a persistent unique tag. Ordered numbers are just an easy way to accomplish that. And in this case if you switch functional group the number part of your identity will still be the same, which is a good thing.
Ok, thanks for your contribution. I accepted your answer because I suspect there is no way to do that. Indeed your argument was mine too, but some people here at my company asked me for that exotic way of identifing requirements
|
Re: Multiple independent identifiers pvselex - Thu Mar 31 09:26:02 EDT 2016 Ok, thanks for your contribution. I accepted your answer because I suspect there is no way to do that. Indeed your argument was mine too, but some people here at my company asked me for that exotic way of identifing requirements
There are other ways to accomplish what you want, by keeping track of counters yourself for the different categories of identities. You can use files for that. Another option is to use "shadow" DOORS modules. When you need to assign a new identity create a new object in the corresponding shadow module and use the new object identfier as identity in your main module. |
Re: Multiple independent identifiers morast - Thu Mar 31 09:47:38 EDT 2016 There are other ways to accomplish what you want, by keeping track of counters yourself for the different categories of identities. You can use files for that. Another option is to use "shadow" DOORS modules. When you need to assign a new identity create a new object in the corresponding shadow module and use the new object identfier as identity in your main module. Ok, I will give the "shadow" module solution a try Thanks |
Re: Multiple independent identifiers pvselex - Thu Mar 31 10:01:25 EDT 2016 Ok, I will give the "shadow" module solution a try Thanks Hi pvselex, Just a hint: I do not know how much time you get by your employer for implementing such a solution, but before you dive into that (it will probably be difficult and time consuming to implement and you might have issues with robustness and with parallel access (remember shared editing!)), you should go back to those "some people" and make sure that you collect the complete set of requirements for your requirement IDs. Those reqs you mentioned in your first post (unique numbers, preserved number for deleted requirements) are fulfilled with morast's solution. Which additional requirements do you have and what is the rationale for them?
One of these requirements to be defined will be to work out a "good" time when to assign a new identity. AFAIK in DOORS 9.6.it is not possible to create a trigger that fires upon object creation, so the users (or a nightly batch or a DOORS admin) might have to start a special script to fill the not-yet-set IDs.
Regards, |
Re: Multiple independent identifiers Mike.Scharnow - Thu Mar 31 11:43:26 EDT 2016 Hi pvselex, Just a hint: I do not know how much time you get by your employer for implementing such a solution, but before you dive into that (it will probably be difficult and time consuming to implement and you might have issues with robustness and with parallel access (remember shared editing!)), you should go back to those "some people" and make sure that you collect the complete set of requirements for your requirement IDs. Those reqs you mentioned in your first post (unique numbers, preserved number for deleted requirements) are fulfilled with morast's solution. Which additional requirements do you have and what is the rationale for them?
One of these requirements to be defined will be to work out a "good" time when to assign a new identity. AFAIK in DOORS 9.6.it is not possible to create a trigger that fires upon object creation, so the users (or a nightly batch or a DOORS admin) might have to start a special script to fill the not-yet-set IDs.
Regards, Hi I appreciate your warning. Don't worry I definitely won't waste my time, except for spending a day or two , just to satisfy my curiosity. Those people I was referring are work colleagues from another department, which was recently fused to my company. They are used to another software suite to capture sw/fw requirements. We are now tryng to armonize our different process standards, tools included For sure, I will stick to DOORS and its natural way of numbering requirements.
Thanks to both of you |